Closed Bug 43253 Opened 24 years ago Closed 23 years ago

PSM needs to be in process.

Categories

(Core Graveyard :: Security: UI, defect, P3)

Product:
Core Graveyard
Component:
Security: UI
Version:
1.0 Branch
Platform:
x86
Windows 98
Type:
defect

Tracking

(Not tracked)

Status:
VERIFIED FIXED

People

(Reporter: jud, Assigned: javi)

References

Details

(Keywords: embed) 

In some embedding situations, an extra process is too expensive. We need to move 
PSM (ssl) over to be in process.
Keywords: embed
Blocks: 48444
-> bob for dispursal.
Assignee: valeski → lord
Updating QA Contact
QA Contact: jrgm → mdunn
A trivial implementation of this has been done for the Mac. Simply building the 
PSM code as a shared library and loading it in process, yet still communicating 
with it via sockets.

This is the plan for PSM 2.0.
Component: Embedding APIs → Client Library
Product: Browser → PSM
Version: other → 2.0
over to default psm owner.
Assignee: lord → ddrinan
QA Contact: mdunn → junruh
re-assigning to myself since ddrinan is on sabbatical
Assignee: ddrinan → javi
Blocks: 64833
Target Milestone: --- → M20
The milestones don't match up.  But we plan on getting this into 0.9
Javi, this one seems to be done. I'm resolving it as FIXED (destroys my stats 
:-) if I keep it open).
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
Verified fixed.
Status: RESOLVED → VERIFIED
Target Milestone: M20 → M18
No longer blocks: 64833
Product: PSM → Core
Version: psm2.0 → 1.0 Branch
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.